-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updating for Visual Studio 2022 #46
Conversation
As written in the link you point to, we can create two installation targets for this extension so that it continues to work for VS2017/19. I believe that VS2017/19 will complain if we release this for VS2022 - they might say it can be updated since it is already installed, although it will not work since this new one will be for x64. So if we continue backward compatibility with 2017/19 we should have two installation targets. Not sure how that will affect the other changes though. UPDATE: Just noticed you had given the extension a new identifier, so then it will not crash. That is probably for the best, but means we don't expect any support to the older ones. |
@@ -39,6 +39,7 @@ public class NUnit2SolutionManager : SolutionManagerBase | |||
{ | |||
private const string NUnitVersion = "2.6.4"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
private const string NUnitVersion = "2.6.4"; | |
private const string NUnitVersion = "2.7.1"; |
|
|
@OsirisTerje I am going to merge this and remove NUnit2 in another PR to keep them separate. |
Continuing work on #43 properly updating the references and updating to the newer framework and adapter releases. Still needs testing. We may need to release a new version just for 2022 now that it is x64?